fix: Reject UpdateDomain requests for deprecated domains #7429
+45
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added validation in the domain handler to reject UpdateDomain requests when the domain status is DEPRECATED.
Why?
Deprecated domains should not be modified. Previously, UpdateDomain would accept requests for deprecated domains, which could lead to:
How did you test it?
TestUpdateDomain_DeprecatedDomain_ReturnsErrorto verify deprecated domains cannot be updatedcommon/domainpackage passPotential risks
Low risk. This change only affects deprecated domains, which are not actively processing workflows. The change is defensive and prevents unintended modifications.
Normal domain operations (registered, active domains) are completely unaffected.
Release notes